-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(protocols): specify raised exceptions (part 2) #1268
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## raises-protocol-handler-no #1268 +/- ##
=============================================================
Coverage ? 84.55%
=============================================================
Files ? 93
Lines ? 16930
Branches ? 0
=============================================================
Hits ? 14315
Misses ? 2615
Partials ? 0
|
f71dd67
to
590e609
Compare
try: | ||
await (await incomingConnection).connection.close() | ||
except: | ||
discard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious about the exception being generated here. Do you think it's worth it to add a trace log?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i internationally didn't wanted to add log there, as compiler tells that AlreadyExpectingConnectionError
can happen here, but, if this error happens it will happen only right after switch.connManager.expectConnection(pid, In)
is called and that case is already handled. however i have added comment (to explain) and error
log (it should never happen tho)
this PR specifies raised exceptions in
protocols
module. it is part 2, continuation to #1260.part of #962 effort.